Collapse All Expand All

The Audit History screen enables users to view a detailed history of all changes and actions taken on an application. All data modified on an application is captured and organized into data collections to give context to the item(s) added, updated, or deleted.

Within the Audit History screen, each modification made to a field is tracked in a grid containing the following columns:

Column Name	Description
Description	Displays a description of the auditable action performed within the application.
User	Displays the name of the user who performed the audit action. For each audit action executed, one of the following may appear to identify the user associated with the action: Name of the Logged In User - appears for actions performed by the end-user as a result of clicking a button or link. Lending System User - appears for actions performed in the background that are not initiated by the end-user, such as automated decisioning, system calculations, and event processing.
Date	Displays the date and time that the audit entry was processed in the application. This information displays in the following format: MM/DD/YY 00:00:00.000.
Type	Displays the type of modification performed.

By default, the Audit History screen displays all modifications made over the previous month, but the information that appears can be adjusted using the following options in the top toolbar:

Sort Option	Description
From/To	Click within the From box and/or To box to display a calendar and specify the date range in which modifications should be returned.
Description	Enter a description of the desired modification within the text box to return all records including the specified text.
Type	Select an element from the drop-down list to filter the results that appear within the Audit History grid. This drop-down contains a list of the audit types recorded for the application.   Select All to display all of the data that has been modified within the application. The Type drop-down defaults to All.
Exclude System Users	Select the check box to exclude all audit actions performed by the Lending System User and only display the audit activity performed by an end user.

Within the top of this screen, users are also provided with the ability to perform the following actions:

Button	Description
	Enables the ability to refresh the Audit History screen and display the most up-to-date information within the grid.
	Enables the ability to export the information that appears within the Audit History screen to Microsoft Excel.
	Enables the ability to print the information that appears within the Audit History screen.

Data Collections

Data within the Audit History grid is organized into collections of audit types. Each collection can be expanded to display detailed information about the changes made and actions taken during the application process.

Each audit type that appears within the Audit History screen consists of a collection of audit actions performed during the application process. These actions include items performed by the end-user, such as updating an application, decisioning an application, or saving a screen, as well as those items that are not directly performed by the end-user such as event processing and calculating an application. Users can expand each element until the updated fields are reached, as well as collapse elements to ensure that only relevant information appears on the screen.

Elements within the Audit History Grid

The first element in each collection displays the initial action performed by the Loan or Account Origination module user, known as the parent action. This action represents the type of auditable information recorded within the audit log.

Reference the following for an overview of the audit types that may appear within the Audit History Screen:

Audit Types

In the example below, a parent action that appears is Save Screen - Phones:

By clicking  next to an element, the parent action can be expanded to view the fields that were modified as a result of that action, as well as any sub-parent records and/or additional actions that may have occurred. Any additional actions recorded are known as child actions. 

As a part of the initial Save Screen action, the application was updated, therefore a sub-parent record of Updated Application appears in the below example:

When this record is expanded, the child actions are displayed. Child actions provide a detailed summary of the auditable items that were added, updated and/or deleted as a result of the initial parent action. Expanding each child action displays the fields that were updated during the action and/or any additional child action(s) that may have been performed.

In the example below, expanding Updated Application provides a record of the applicant that was updated, which can then be further expanded to view the specific phone information that was saved within the screen.

The audit descriptions for each child action are populated by a specific formula within the database. For some audit descriptions, this formula pulls from user-defined lookup values in Field Configurations. For example, when phone information is updated as shown in the example above, the formula pulls the value from the PHONE_TYPE lookup. Since the values within the PHONE_TYPE lookup can be modified, the system administrator can configure how the audit description appears within the Audit History screen.

The following table provides an overview of the items that may appear for audit, the formula that is used to populate the item and an example of how the information is presented within the Audit History screen:

Audit Item	Formula	Example
Address	{ADDRESS_TYPE} Address – [Address1]	Added Current Address – 111 Sesame Street
Aggregate	{AGGREGATE} Aggregate	Added Total Annual Income Aggregate
Applicant	(Applicant Type) – [Full Name] The value that appears for Applicant Type is populated from the Lending.ApplicantType table in the database. The applicant type identified for an applicant, either through Make Primary, the Add Applicant window or Applicant Type drop-down, is the value that populates in the Audit History.	Updated Joint Applicant – Doc Brown
Application Funding	{FUNDING_TYPE} Funding – [Amount]	Added Check Funding – 25000.00
Asset	{ASSET_TYPE} Asset	Deleted Vehicle Asset
Authorized User	Authorized User – [First Name] [Last Name]	Added Authorized User – Jane Doe
Collateral	{COLLATERAL_CODE} Collateral	Updated Real Estate Collateral
Counteroffer Aggregate	{AGGREGATE} Aggregate	Added Available Equity Aggregate
Counteroffer Ratio	{RATIO} Ratio	Added Loan To Value Ratio
Income	{INCOME_SOURCE} Income	Deleted Retirement Income
Liability	{TRADE_TYPE} Liability	Added Installment Liability
Payee	Payee – [First Name] [Last Name]	Added Payee – Marty McFly
Phone	{PHONE_TYPE} Phone	Updated Home Phone
Ratio	{RATIO} Ratio	Added Loan Payment To Income Ratio
Reference	{REFERENCE_TYPE} Reference – [Full Name]	Added Relative Reference – John Doe
Stipulation	{STIPULATION_CODE} Stipulation	Added Proof of Identification Stipulation
To-Do	[Text] To-do	Updated Paystub Required To-do
Vendor	Vendor – [Name]	Added Vendor – Temenos Demo

 

 

---

©2022 Temenos Headquarters SA - all rights reserved.

Send Feedback